Installing Web Access on a different server

In many situations, a different server already running IIS is available for hosting Meridian Web Access. This is a valid configuration so long as DCOM access is possible between the Web Access server and the Meridian server. For help installing Web Access with a firewall, see Allowing Web Access through a firewall. The minimum IIS components that must be installed for proper operation of Web Access are listed in Recommended server specifications.

To install the Web Access server components on a server other than the Meridian application server:

1. Start the Meridian setup program on the Web Access server.
2. Select Server or Customized Setup.
3. From the Server components list, select only Web Access. Do not install the License Server component or any client components. The Administrator components will be installed with Web Access because they are needed to create web locations of the vaults.
4. When prompted, type the name of the computer running the AutoManager EDM Server service.

Note    In this configuration, user login credentials will be required to authenticate the Web Access server to the Meridian application server. You must enable either the Integrated Windows Authentication or Basic Authentication options of the website so that user credentials are obtained every time Web Access is used.

Note    If the computer is running a 64-bit version of Windows and 32-bit Web Access components are installed, set the registry keys described in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\InetStp\Components. In this configuration, the Meridian website must run in a 32-bit application pool. For more information on how to create a 32-bit application pool, refer to Running 32-bit Applications on 64-bit Windows (IIS 6.0) in Microsoft TechNet.